Cable Management System and Method

ABSTRACT

A cable management system includes multiple cables, each having a unique identifier associated therewith and each including first and second barcodes including the unique identifier, the first barcode located proximate a first end of the cable, the second barcode located proximate a second end of the cable. The system also includes a barcode scanner to scan barcodes of the cables, the barcode scanner including a clip to receive one of the cables. The system also includes a mobile computing device having a processor, data storage medium, communication unit, and user interface including a display. The mobile computing device is configured to receive via the user interface first end location information for a first cable, receive from the barcode scanner the first barcode of the first cable, and save and display the first end location information in association with the unique identifier of the first cable included in the first barcode.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims benefit to U.S. Provisional Patent ApplicationNo. 62/986,890, filed Mar. 9, 2020, and also claims benefit to U.S.Provisional Patent Application No. 63/056,092, filed Jul. 24, 2020, theentirety of all of which are incorporated by reference herein.

TECHNICAL FIELD

The following relates to a device, system, method, and non-transitorycomputer readable medium for managing cables in a telecommunications ordata center.

BACKGROUND

Datacenters and telecommunications rooms utilize cabling to communicatelarge amounts of data. Some data centers can have several hundredthousand cables. It follows that cable management is time consuming,labor intensive work. Today there are two known approaches in widespreaduse.

A first known approach is manually tracing each cable and documentingthe physical location of each cable end (i.e., cable end #1 is locatedon port 3 of patch panel “A” and cable end #2 is located on port 5 ofpatch panel “B”). This approach takes time and relies on staticdocumentation which can grow stale quickly without constant updating andattention. If data center infrastructure management (DCIM) or some othercable management software is used, the cable location information mustbe entered manually.

A second known approach is to use no documentation. That is, cableinfrastructure is not documented and instead cables are traced on an “asneeded” basis. Too often this tracing is done after an outage occurswhich can extend downtime and revenue loss.

Neither of these approaches are optimal as the first takes time and thy:second can prolong time to recovery during a failure. In that regard,data center outages can cause an enterprise to lose valuable resourcesas well as result in high costs to remediate. A solution that reducesthe time spent tracing cables can save money and resources duringinstallation and maintenance, as well as reducethe Mean Time To Recovery(MTTR.) during system outages. Anything that can help reduce downtimeduring an outage c .n result° ficant sayings.

A need therefore exists for a cable management device, system, method,and application program designed to trace cables more efficiently aswell as quickly audit existing installations and dynamically upload datato cable management systems.

SUMMARY

According to one non-limiting exemplary embodiment described herein, acable management system is provided. The system comprises a plurality ofcables, wherein each of the plurality of cables has a unique identifierassociated therewith, and wherein each of the plurality of cablescomprises a first barcode and a second barcode, the first barcodeincluding the unique identifier and located proximate a first end of thecable, the second barcode including the unique identifier and locatedproximate a second end of the cable. The system further comprises abarcode scanner configured to scan barcodes of the plurality of cables,wherein the barcode scanner comprises a clip configured to receive oneof the plurality of cables. The system further comprises a mobilecomputing device comprising a processor, a data storage medium, acommunication unit, and a user interface including a display, whereinthe mobile computing device is configured to receive via the userinterface first end location information for a first one of theplurality of cables, receive from the barcode scanner the first barcodeof the first one of the plurality of cables, and save and display thefirst end location information in association with the unique identifierof the first one of the plurality of cables included in the firstbarcode.

According to another non-limiting exemplary embodiment described herein,a method for managing a plurality of cables is provided, wherein each ofthe plurality of cables has a unique identifier associated therewith,and wherein each of the plurality of cables comprises a first barcodeand a second barcode, the first barcode including the unique identifierand located proximate a first end of the cable, the second barcodeincluding the unique identifier and located proximate a second end ofthe cable. The method comprises identifying first end locationinformation for a first one of the plurality of cables, scanning thefirst barcode of the first one of the plurality of cables with a barcodescanner comprising a clip configured to receive the first one of theplurality of cables, and storing in a data storage medium the first endlocation information in association with the unique identifier of thefirst one of the plurality of cables included in the first barcode.

According to yet another non-limiting exemplary embodiment describedherein, a non-transitory computer readable storage medium having storedcomputer executable instructions for managing a plurality of cables isprovided, wherein each of the plurality of cables has a uniqueidentifier associated therewith, and wherein each of the plurality ofcables comprises a first barcode and a second barcode, the first barcodeincluding the unique identifier and located proximate a first end of thecable, the second barcode including the unique identifier and locatedproximate a second end of the cable. Execution of the instructionscauses a processor to receive first end location information for a firstone of the plurality of cables, receive from a barcode scanner the firstbarcode of the first one of the plurality of cables, and store in a datastorage medium the first end location information in association withthe unique identifier of the first one of the plurality of cablesincluded in the first barcode.

A detailed description of these and other non-limiting exemplaryembodiments of a cable management system, method, and non-transitorycomputer readable storage medium is set forth below together with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a plurality of network cables connected between two patchpanels, according to a non-limiting exemplary embodiment of the presentdisclosure.

FIG. 2 shows a cable with unique identifiers on each end thereof,according to a non-limiting exemplary embodiment of the presentdisclosure.

FIG. 3 shows a patch cable with a machine-readable unique identifierproximate an end of the cable, according to a non-limiting exemplaryembodiment of the present disclosure.

FIG. 4 shows a simplified block diagram of a cable management system,according to a non-limiting exemplary embodiment of the presentdisclosure.

FIG. 5A shows a perspective view of a scanning clip for use with abarcode scanner to scan a unique identifier of a cable, according to anon-limiting exemplary embodiments of the present disclosure.

FIG. 5B shows a perspective view of the scanning clip shown in FIG. 5A,where the scanning clip is attached to a barcode scanner for scanning aunique identifier of a cable, according to a non-limiting exemplaryembodiments of the present disclosure.

FIG. 6 shows a mobile computing device, which may comprise a display,data storage medium, and processor configured to execute computerreadable instructions to implement a cable management tool, according toa non-limiting exemplary embodiment of the present disclosure.

FIG. 7 shows a mobile computing device, which may comprise a display,data storage medium, and processor configured to execute computerreadable instructions for entering a “scan” mode, according to anon-limiting exemplary embodiment of the present disclosure.

FIG. 8 shows a mobile computing device, which may comprise a display,data storage medium, and processor configured to execute computerreadable instructions for receipt and/or entry of networking deviceinformation in the “scan” mode, according to a non-limiting exemplaryembodiment of the present disclosure.

FIG. 9 shows a mobile computing device, which may comprise a display,data storage medium, and processor configured to execute computerreadable instructions for receipt and/or entry of port information inthe “scan” mode, according to a non-limiting exemplary embodiment of thepresent disclosure.

FIG. 10 shows a mobile computing device, which may comprise a display,data storage medium, and processor configured to execute computerreadable instructions for generating and displaying output of matchingunique identification tags and corresponding physical ports in the“scan” mode, according to a non-limiting exemplary embodiment of thepresent disclosure.

FIG. 11 shows a mobile computing device, which may comprise a display,data storage medium, and processor configured to execute computerreadable instructions for entering a “scan and verify” mode, accordingto a non-limiting exemplary embodiment of the present disclosure.

FIG. 12 shows a mobile computing device, which may comprise a display,data storage medium, and processor configured to execute computerreadable instructions for receipt and/or entry of panel name and portnumber information of a next port to scan in the “scan and verify” mode,according to a non-limiting exemplary embodiment of the presentdisclosure.

FIG. 13 shows a mobile computing device, which may comprise a display,data storage medium, and processor configured to execute computerreadable instructions for generating and displaying output results of“pass” and “fail” statuses for cables in the “scan and verify” mode,according to a non-limiting exemplary embodiment of the presentdisclosure.

FIG. 14 shows a mobile computing device, which may comprise a display,data storage medium, and processor configured to execute computerreadable instructions for entering a “find” mode, according to anon-limiting exemplary embodiment of the present disclosure.

FIG. 15 shows a logic flowchart describing a process for a “scan” modeand a “scan and verify” mode implemented using the cable managementtool, according to a non-limiting exemplary embodiment of the presentdisclosure.

FIG. 16 shows a logic flowchart describing a process for a “find” modeimplemented using the cable management tool, according to a non-limitingexemplary embodiment of the present disclosure.

FIG. 17 shows a structured cabling system installed in an environmentwhere the cable management tool is being executed, according to anon-limiting exemplary embodiment of the present disclosure.

FIG. 18 shows a cable with unique identifiers pre-printed atpredetermined intervals on an outer layer of the cable according to onenon-limiting exemplary embodiment of the present disclosure.

FIG. 19 shows a logic flowchart describing an exemplary installationprocess implemented by the cable management tool using the cableillustrated in FIG. 18.

DETAILED DESCRIPTION

In this disclosure, detailed non-limiting embodiments are disclosedherein. However, it is to be understood that the disclosed embodimentsare merely exemplary and may take various and alternative forms. Thefigures are not necessarily to scale, and features may be exaggerated orminimized to show details of particular components. Therefore, specificstructural and functional details disclosed herein are not to beinterpreted as limiting, but merely as a representative basis forteaching one skilled in the art.

With reference to the figures, a more detailed description ofnon-limiting exemplary embodiments of a cable management device, system,method, and non-transitory computer readable medium will be provided.For ease of illustration and to facilitate understanding, like referencenumerals have been used herein for like components and featuresthroughout the drawings.

As previously described, a need e Isis for a cable m anagement device,system, method, and application program designed to save time fromtracing cables as well as create a way to quickly audit existinginstallations and dynamically upload data to cable management systems.

The present disclosure provides a cable management device, system,method, and non-transitory computer readable storage medium thataddresses and/or meets such a need and solves the problems associatedwith the known cable management approaches described previously. Thecable management device, system, method, and non-transitory computerreadable storage medium of the present disclosure provide and/or utilizeunique cable identifiers in conjunction with intelligence that canprovide patch field cable documentation without the hassle of manuallytracing cables and documenting their location. Once a patch field hasbeen scanned, the cable management device, system, method, andnon-transitory computer readable storage medium of the presentdisclosure can then use saved information to verify or find existingconnections.

The cable management device, system, method and non-transitory computerreadable medium of the present disclosure for identifying anddocumenting connections between patch panel ports may comprise, provide,and/or utilize one or more patch panels or pieces of equipment withmultiple network ports for connecting cables. The cable managementdevice, system, method, and non-transitory computer readable medium ofthe present disclosure may further comprise, provide, and/or utilizevarious features as described herein.

The cable management device, system, method, and medium may comprise oneor more cables 10 connected between patch panels 14, 16 as seen inFIG. 1. Although this disclosure describes the cables 10 being connectedbetween patch panels 14, 16 according to exemplary embodiments, thecable management solution described herein may be implemented such thatthe cables 10 are connected between other networking devices such asservers, switches, routers, or other networking devices where cables areinstalled.

FIG. shows a plurality of network cables 10 connected between a firstpatch panel A 14 and a second patch panel B 16 according to anon-limiting exemplary embodiment of the present disclosure. One or moreof the cables 10 have a label 12 attached, where the label 12 includes aunique identifier 13 (i.e., collectively may be referred to as a “uniqueID cable”). A unique ID cable may comprise a network patch cable 10including a unique identifier 13 that has been attached, affixed, orplaced at or proximate each end of the cable 10. According to someembodiments, the unique identifier 13 is placed a predetermined distancefrom the ends of the cable 10 such as within 3 inches of one, or both,ends of the cable 10, or within a range of 0.25 to 6 inches from one, orboth, ends of the cable 10. According to some embodiments, the uniqueidentifier 13, is placed to provide a predetermined distance (e.g., 2inches with a 0.5 inch tolerance) between the end of the cable plug bootto the edge of the label 12. According to some embodiments, the uniqueidentifier 13 is placed at a predetermined location (e.g., distance fromthe ends of the cable 10 such as between 0.25 to 6 inches from one, orboth, ends of the cable 10) based on the type of cable 10 being used(e.g., CAT6, shielded, breakout, fiber, etc.).

According to the illustrated embodiments in FIG. 2, the uniqueidentifier 13 is printed onto a label 12 and affixed onto the cable 10,where the unique identifier 13 is printed in the form of barcodes.However, according to other embodiments the unique identifier 13 may beprinted or etched directly onto the cable 10. .Further, the uniqueidentifier 13 may take on other forms of machine-readable codes such asa QR code, alphanumeric passcodes, or other passively detectable forms.The unique identifier 13 is representative of an identification codeassociated to the cable 10, and for corresponding the cable 10 withadditional information such as installation location, production data,and/or cable attribute data.

FIG. 2 depicts a cable 10 with a label 12 having a unique identifier 13on each end thereof according to a non-limiting exemplary embodiment ofthe present disclosure. In a system of multiple cables 10, each uniqueidentifier 13 is produced to identify a respective unique cable 10and/or the location where each end of the cable 10 is installed. Soaccording to some embodiments, the unique identifier 13 placed on eachrespective ends of a unique cable 10 will be slightly different toidentify which end of the cable 10 the unique identifier 13 has beenplaced on. For example, the barcode placed at a first end A maycorrespond to a first identification code, and the barcode placed at asecond end B may correspond to a second identification code, where thefirst and second identification code are mostly comprised of the sameidentification code other than a slight difference to identify theirrespective placement at the first end A or the second end B (e.g.,10000090A and 10000090B). FIG. 3 depicts a patch cable 10 with themachine-readable unique identifier 13 proximate an end of the cable 10according to a non-limiting exemplary embodiment of the presentdisclosure. Specifically, the unique identifier 13 is placed at apredetermined location on the cable 10 (e.g., predetermined distancefrom a plug 17 that terminates an end of the cable 10 shown in FIG. 3).

FIG. 4 is a simplified block diagram of a cable management system 200according to a non-limiting exemplary embodiment of the presentdisclosure. As seen therein, the system 200 comprises a mobile computingdevice 20, such as a tablet, smartphone, laptop, or other mobilecomputing device. The mobile computing device 20 may comprise a display24, a data storage medium or memory 26, and a processor 28 configured toexecute a cable management program or soft re according to the presentdisclosure (which application program may be referred to s the “cablemanagement tool”).

The system 200 may further comprise a barcode scanner 30, such as ageneral-purpose scanning device which may be used to scan the uniqueidentifier 13 (e.g., barcode identifier) attached to the cable 10, andto communicate barcode information to the mobile computing device 20.Such communication may be accomplished via wired or wireless connection32 between the barcode scanner 30 and the mobile computing device 20.According to other embodiments, the barcode scanner 30 may be replacedwith a different detection device that is either a stand-alone device orintegrated into the mobile computing device 20 capable of reading theunique identifier 13 (e.g., digital video camera, digital image camera,RFID reader, or the like).

The system 200 may still further comprise a scanner clip 34 that isattached, affixed, or otherwise mounted to the barcode scanner 30.Alternatively, the scanner clip 34 may be an integral part of orintegrated with the barcode scanner 30. The scanner clip 34 includes aviewing window 36 formed therein for allowing a user operating thebarcode scanner 30 to view the unique identifier 13 of the cable 10 thatis being held by the scanner clip 34. The viewing window 36 may be acut-out portion, or made from a sheet of non-opaque material. Accordingto some embodiments, the viewing window 36 may not be included. Thescanner clip 34 includes a hook portion 38 configured to receive/graband isolate the individual cable 10 having the identifier 13 to bescanned, as will be described in more detail with reference to FIGS. 5Aand 5B.

In that regard, FIGS. 5A and 5B are perspective views of the scannerclip 34 for use with the barcode scanner 30, where the scanner clip 34is configured to hold the cable 10 while the barcode scanner 30 scansthe unique identifier 13 according to non-limiting exemplary embodimentsof the present disclosure. As illustrated in FIG. 5A, the scanner clip34 includes mounting features 37 configured to attach, affix, or mountthe scanner clip 34 to the barcode scanner 30.

FIG. 5B depicts the scanner clip 34 attached, affixed, or mounted to ascanning end of the barcode scanner 30. As seen therein, the hookportion 38 of the scanner clip 34 is configured to receive/grab andisolate the individual cable 10 to bring the unique identifier 13 intoview of a scanning input window at the scanning end of the barcodescanner 30. The viewing window 36 in the scanner clip 34 enables a userholding the barcode scanner 30 to view the unique identifier 13 throughthe viewing window 36 as the cable 10 is being held by the hook portion38. The scanner clip 34, therefore, enables the individual cable 10 tobe quickly and easily isolated from other neighboring cables so that itsunique identifier 13 can be successfully and accurately scanned forinput into the cable management tool. This way, the scanner clip 34helps increase the efficiency of the scanning processing for identifyingand associating a large number of cables installed into panels 14, 16and port numbers by reducing the time needed to do so in a system ofpatch panels as shown in FIG. 1.

Referring again to FIG. 4, the cable 10 may be any type including, butnot limited to, copper wire ethernet cable, fiber optic cable,hi-density fiber cable, or breakout cable. The cable 10 may comprise thelabel 12 including the unique identifier 13 near each end thereof, wherethe label 12 may take the form of a printed label attached or affixed tothe cable 10 proximate each end thereof. The unique identifier 13according to the described embodiments are barcodes, where the barcodesare used to obtain an identification code that is used to look-up therespective cable 10, the cable's 10 to/from installation location,and/or cable production data such as, but not limited to, cablemanufacturing information (e.g., cable length, part number, cable type),quality control data, country of origin, production date, material lotnumber, category of cable, plenum or LSZH material confirmation, testresult data such as insertion loss, crosstalk, DC resistance, or otherinformation known about the cable (hereinafter collectively referred toas the cable information). The unique identifier 13 is created touniquely correspond to each associated cable 10 included in the system.To enable the look-up function, the identification code obtained fromscanning the unique identifier 13 and the corresponding cableinformation may be stored as part of a lookup table or database that ispart of the cable management tool described herein. In the case of abreakout cable, the cable ID may include a decimal format (e.g., 1.1,1.2, 1.3, etc.) to account for the single breakout cable including aplurality of individual cables that fan out from the main breakout cableformation.

It should be noted that the mobile computing device 20, the barcodescanner 30, and/or any other computing unit, module, controller, system,subsystem, mechanism, device, component or the like described herein maycomprise appropriate circuitry, such as one or more appropriatelyprogrammed processors (e.g., one or more microprocessors includingcentral processing units (CPU)) and associated memory or data storagemedium, which may include stored operating system software and/orapplication software executable by the processor(s) for controllingoperation thereof and for performing the particular algorithmsrepresented by the various functions and/or operations described herein,including interaction and/or communication between and/or cooperationwith each other. One or more of such processors or several suchprocessors and/or circuitry and/or hardware may be distributed amongseveral separate units, modules, controllers, systems, subsystems,mechanisms, devices, components or the like.

The cable management tool may be an app installed onto the mobilecomputing device 20 for use in performing the cable management method ofthe present disclosure, and which may be implemented at least in part asmachine (e.g., computer) executable instructions stored on or in anon-transitory computer readable storage medium. The cable managementtool may further include software, hardware, middleware, applicationprogramming interface, circuitry, and/or other components forimplementing the features described herein that relate to the cablemanagement tool.

The cable management tool may be configured to run or be executed by theprocessor 28 of the mobile computing device 20 to manage and locate thelarge number of cables 10 that are found attached to patch panels 14, 16installed on a network rack (see e.g., FIG. 1). The cable managementtool is configured to receive the unique identifier 13 information fromthe barcode scanner 30 and identify the identification code representedby the barcode. Then, the cable management tool is configured to searchor lookup, in a database or table, the cable information associated tothe identification code. For example, the cable management tool maycommunicate, via an application programming interface (API), with anoffsite server to access the database or table stored on the server. Thecable information stored within the database or table may be downloadedonto the mobile computing device 20 using the cable management tool, andfurther be printed onto labels. Communication with the server may beimplemented via either the wired or wireless connection 32 provided bythe mobile computing device 20.

The cable management tool may operate within the cable management system200 in any of three modes: 1) Scan Mode; 2) Scan and Verify Mode; or 3)Find Mode. The cable management tool may also be configured to generatereports detailing the cable locations. Such reports can be exported oruploaded to a data storage medium, such as cloud storage, which maycomprise a database, transmitted to another user at a remote location,and/or stored on memory storage included in the mobile computing device20. The report may be in a flat file format according to someembodiments.

FIG. 6 shows an exemplary view of the mobile computing device 20executing the cable management tool, and displaying a graphical userinterface (GUI) of the cable management tool on the display 24. Asdescribed, the mobile computing device 20 includes the hardware,software, and/or circuitry for executing the cable management tool. Inparticular, the machine-readable instructions that comprise the cablemanagement tool are stored in the memory 26, and the processor 28 readsthese machine-readable instructions and executes them to run the cablemanagement tool according to the present disclosure.

As previously described, the cable management system 200 includes thebarcode scanner 30 which may be connected via Bluetooth, UniversalSerial Bus (USB), or any other type of wired or wireless connection 32to the mobile computing device 20 configured to run the cable managementtool. Once again, the cable management system u0 further comprises thebarcode scanner clip 34 used to isolate the individual cable 10 from aplurality of surrounding cables, to scan the unique identifier 13 fromthe cable 10.

As previously noted, the cable management tool may operate in oraccording to various modes. Such modes may comprise a “scan” mode, a“scan and verify” mode, and a “find” mode for managing cables as a frontof panel solution where cables are being installed between networkingdevices. Various non-limiting steps, functions, functionality,operations, features, and/or processes for such modes will now bedescribed. In that regard, it should he noted that such steps,functions, functionality, operations, features, and/or processes may beperformed at different times, in an order or orders other than thosedescribed, and/or that one or more may be omitted. The “scan” mode, the“scan and verify” mode, and the “find” mode, may each comprise one ormore of the following steps 1-6:

Step 1: Start with an existing patch field that incorporates the uniqueID cables described herein. The existing patch field may comprise one ormore patch panels 14, 16 (see FIG. 1) containing multiple ports. Thepatch field utilizes unique ID patch cables 10 to make connectionsbetween two ports in the patch field.

Step 2: Run the cable management tool on the mobile computing device 20.Once again, FIG. 6 depicts the mobile computing device 20 displaying aGUI on the display 24 of the mobile computing device 20 based on anexecution of machine-readable instructions of the cable management tool,according to a non-limiting exemplary embodiment of the presentdisclosure.

Step 3: Change, enter, and/or set the software mode to “scan” mode. Inthat regard, FIG. 7 depicts the mobile computing device 20 executingmachine-readable instructions for running the “scan” mode 40 anddisplaying a GUI of the “scan” mode 40 on the display 24, according to anon-limiting exemplary embodiment of the present disclosure.

Step 4: Enter the name of the patch panel being scanned into the “PanelName” field. FIG. 8 depicts the mobile computing device 20 executingmachine-readable instructions for running the “scan” mode 40 to enableentry of patch panel name information into the “Panel Name” informationentry field 42 included in the GUI of the “scan” mode 40 displayed onthe display 24, according to a non-limiting exemplary embodiment of thepresent disclosure. A user may utilize an input device (e.g., touchscreen keyboard, mechanical keyboard, speech input, or the like) toenter the patch panel name information into the “Panel Name” informationentry field 42.

Step 5: Enter the port number into the “Scanning Port” field. In thatregard, FIG. 9 depicts the mobile computing device executingmachine-readable instructions for running the “scan” mode 40 to enableentry of port number information into the “Scanning Port” informationentry field 44 included in the GUI of the “scan” mode 40 displayed onthe display 24, according to one non-limiting exemplary embodiment ofthe present disclosure. A user may utilize an input device (e.g., touchscreen keyboard, mechanical keyboard, speech input, or the like) toenter the port number information into the “Scanning Port” informationentry field 44.

Step 6: Scan the unique identifier 13 of the cable 10 associated withthe atch panel and port entered. After scanning the unique identifier 13with the barcode scanner 30, the port number in the “Scanning Port”information entry field 44 (see e.g., FIG, 9) increments by oneautomatically to allow data entry at the next port. If the incrementedport number displayed in the “Scanning Port” information entry field 44is not correct, the user may manually enter the next patch panel nameand/or correct next port number to scan in information. This process iscontinued until all cables 10 connected to ports have been scanned.

Step 7: While the user is scanning the unique identifier 13 of thecables10, the cable management tool stores the information obtained fromscanning the unique identifier 13 in a database along with thecorresponding panel and port number e., location information). The cablemanagement tool is now able to accurately locate matching uniqueidentifiers and correlate them to the associated cables and theirphysical patch panel and port locations. The cable management tool mayalso display these matches on the display 24 of the mobile computingdevice 20 as connections.

In that regard, FIG. 10 depicts the display 24 of the mobile computingdevice 20 displaying an output GUI that matches unique identifier tagswith their corresponding physical port information 1001 a, 1001 b in the“scan” mode 40, according to a non-limiting exemplary embodiment of thepresent disclosure. These results can be exported 48 and/or transmittedas desired, such as to a remote user, a data storage medium such ascloud storage (which may comprise a database), an excel spreadsheet, ora comma separated values file for import into other management systems.

For example, data may be exported via a comma-separated text file (.csvfile extension). Each file represents a telecom room or data center. Thelocation fields may be manually entered in the cable management tool,where the ID fields are the value of the scanned unique identifier 13.As seen in FIG. 10, the output fields may be Near End port location (NEPort) 1010, Near End ID Number (NE ID) 1020, Far End port location (FEPort) 1030, Far End ID number (FE ID) 1040. Sample output for suchfields in a comma separated .csv file format with the data shown in FIG.10 may appear as follows:

SwtchA-01,10000090,Panel-28,10000090

SwtchA-02,10000059,Panel-27,10000059

SwtchA-03,10000001,Panel-26,10000001

SwtchA-04,10000012,Panel-25,10000012

The “scan and verify” mode 50 may further comprise one or more steps8-10 as described below with reference to FIGS. 11-13 Once again, itshould be noted that such steps, functions, functionality, operations,features, and/or processes may be performed at different times, in anorder or orders other than those described, and/or that one or more maybe omitted.

Step 8: Select “scan and verify” mode 50. In that regard, FIG. 11depicts the mobile computing device 20 executing machine-readableinstructions for entering the “scan and verify” mode 50, according to anon-limiting exemplary embodiment of the present disclosure. In FIG. 11,a GUI corresponding to the “scan and verify” mode 50 is displayed on thedisplay 24 of the mobile computing device 20. The “scan and verify” mode50 uses previously saved results from the “scan” mode 40 (see e.g.,FIGS. 7-10) operation to verify liether cables 10 have moved since thelast scanning. If saved results do not exist, steps 1 through 6described previously are performed. in addition or alternatively,according to some embodiments the saved results used for verificationmay be downloaded as a set of predetermined installation locationresults so that the current scanning operation can be compared agai nst.

Step 9: Enter panel name and port number of the current patch panel portlocation to be verified. FIG. 12 depicts the mobile computing device 20executing machine-readable instructions for running the “scan andverify” mode 50 to enable entry of patch panel name information into the“Panel Name” information entry field 52 included in the GUI of the “scanand verify” mode 50 displayed on the display 24, according to anon-limiting exemplary embodiment of the present disclosure. FIG. 12also depicts the mobile computing device 20 executing machine-readableinstructions for running the “scan and verify” mode 50 to enable entryof scanning port name information into the “Scanning Port” informationentry field 54 included in the GUI of the “scan and verify” mode 50displayed on the display 24, according to a non-limiting exemplaryembodiment of the present disclosure. A user may utilize an input device(e.g., touch screen keyboard, mechanical keyboard, speech input, or thelike) to enter the patch panel name information into the “Panel Name”information entry field 52 as well as the scanning port name informationinto the “Scanning Port” information entry field 54.

Step 10: Scan unique identifier 13 of the cable 10 in a selected port.The cable management tool identifies the current cable 10 based thescanned unique identifier 13, and looks up its correspondinginstallation location fo ion from the stored database that tracks itspanel and/or port installation location information from the last timeit has been scanned (or based on previously downloaded installationlocation data). The comparison is then given a PASS/FAIL, grade based onwhether the comparison of the inputted location from Step 9 matches thepreviously installed location information looked up in Step 10 (PASS) ordoes not match (FAIL), and a corresponding notification may be output tothe display 24. In that regard, FIG. 13 depicts the mobile computingdevice 20 displaying the results of the PASS/FAIL status information 55(which may take the form of color-coded information, such as green forpass and red for fail, or other visual indicator such as a flag or othersymbol to identify failing status or passing status) based on thecomparison in the “scan and verify” mode 50, according to onenon-limiting exemplary embodiment of the present disclosure. If thecurrent location information that has been inputted matches the storedand expected location information for the cable that has been identifiedfrom the stored database based on the scanned unique identifier 13, a“pass” status is reported. If the current location does not match thestored database record for that cable's identification code obtainedfrom the scanning of the unique identifier 13, a “fail” status isreported. The fail status also reports the last recorded cableidentification code 56 (cable identification code 10000007 Expected NearEnd ID (Exp NE ID)) for that location as an expected identifier value.

The “find” mode 60 may further comprise steps 11-13 as described belowwith reference to FIG. 14. Once again, it should be noted that suchsteps, functions, functionality, operations, features, and/or processesmay be performed at different times, in an order or orders other thanthose described, and/or that one or more may be omitted.

Step 11: Select the “find” mode 60. In that regard, FIG. 14 depicts themobile computing device 20 executing machine-readable instructions forentering the “find” mode 60, according to one non-limiting exemplaryembodiment of the present disclosure. FIG. lA shows a GUI that isdisplayed on the display 24 of the mobile computing device 20 accordingto the “find” mode 60. The “find” mode 60 is useful when one end of thecable 10 has been located and it is desired to find the other end ofthat same cable 10. With the “find” mode 60, there is a first knowncable 10 that a user is trying to match and there are target cables 10that could potentially be the other end of the first known cable 10.

Step 12: Scan the unique identifier 13 on the first end of the cable 10(i.e., first location). Once the unique identifier 13 at the first endhas been scanned, the cable identification code corresponding to thisscanned unique identifier 13 is obtained as this first cableidentification code represents the cable ends trying to be found. Thenall following cable identification codes that are obtained fromsubsequent scans of unique identifiers 13 in Step 13 shile in the “find”mode are compared against this first cable identification code and givena PASS status when the subsequently obtained cable identification codematches the first cable identification code, and a FAIL status when thesubsequently scanned unique identifier 13 does not match the firstunique identifier 13.

Step 13: Scan subsequent unique identifier 13 at a second end of thecable 10 (i.e., second location) to obtain the cable identification codefor the unknown cable end at the second location. While in this “find”mode, each of the cable identification codes that are obtained from thescanning of subsequent unique identifier 13 at the second location arecompared against the first cable identification code and given a PASSstatus when the subsequently obtained cable identification code matchesthe first cable identification code, and a FAIL status when thesubsequently obtained cable identification code does not match the firstcable identification code. The status may be reported to the user viadisplay onto the “find” mode GUI displayed on the display 24.

As previously noted, in each of the “scan” mode 40, “scan and verify”mode 50, and “find” mode 60, the cable management tool may also beconfigured to generate reports detailing the cable installationlocations. Such results can also be saved, exported, and/or transmittedas desired, such as to a remote user or remote location, a data storagemedium such as cloud storage (which may comprise a database), an excelspreadsheet, or a comma separated values file for import into othermanagement systems. The GUI shown in FIG. 14 includes a save button 61and an export button 62 to implement these respective functions. Thecable management tool may also be configured to provide an option forthe ser to save and move on, or save and quit, after each scan and/orafter ach tip e new data is input to the lookup table storing the cableinformation.

FIG. 15 is a logic flowchart 1500 describing a process implemented bythe cable management tool for the “scan” mode 40 and the “scan andverify” mode 50 described herein, according to a non-limiting exemplaryembodiment of the present disclosure. As shown, the cable managementtool may start execution based on two scenarios (72): first, a newinstallation environment where unique ID cables have not yet been fullyinstalled (74); or second, a previously installed environment whereunique ID cables have already been partially, or fully, installed (76).Upon starting execution of the cable management tool (72), the cablemanagement tool may enter the “scan” mode 40, the “scan and verify” mode50, or the “find” mode 60.

As previously described and shown in the flowchart 1500, the “scan” mode40 proceeds with the cable management tool receiving panel nameinformation (80) and port number information (82). For example, thepanel name information and/or port number information may be enteredinto their respective fields in the GUI via an input device (e.g.,keyboard or touchscreen), or in some embodiments received from anotherdata source.

Thereafter the unique identifier on the current cable is scanned (84),where the information obtained from scanning the unique identifier maybe used to create or add to a database (86). For example, the cablemanagement tool obtains a cable identification code based on the scannedunique identifier, and creates a database entry for the cable under theobtained cable identification code. Then, the database storescorresponding cable information to associate with the database entry forthe cable identification code. Such cable information may include ormore of cable ends installation location, cable production data, and/orother cable attribute information that is accessed based on the cableidentification code. Thus the database becomes an effective andefficient store of relevant information for an installer to access as itidentifies the cables used in the installation and associates them totheir corresponding cable information. The database may be constructedas, for example, a lookup table format.

After such scanning (84), the port number is automatically incremented(88), and the cable management tool comes to a decision point where adetermination is made as to whether the next port number is, or will be,populated with a cable (90). If so, the cable management tool goesthrough the looped process of scanning the unique identifier of the nextcable to obtain the cable identification code of the next cable (84),adding the next cable's identification code to the database as well asaccessing any known cable information to the database entry (86), andautomatically incrementing the port number (88). Otherwise, the cablemanagement tool determines whether all cables associated with thecurrent panel have been scanned (92). If not, then the process for the“scan” mode 40 moves to the next port populated with a cable on thecurrent panel (94). Otherwise, the cable management tool determineswhether all scanning has been completed for additional panels (96). Ifthere are additional panels left for scanning, then the process for the“scan” mode 40 moves to a new panel (98). Otherwise, when there are nomore panels for scanning the process for the “scan” mode 40 ends (100).

As also previously described, the “scan and verify” mode 50 may proceedwith loading saved result for scanned cables from a database (102). Thesaved results may be obtained from a previous iteration of the “scan”mode, or previously downloaded cable installation results. Panel nameinformation and port number information is then entered into the cablemanagement tool and/or received by the cable management tool (104).

Thereafter, a unique identifier of a current cable is scanned (106), anda PASS/FAIL result is reported by the cable management tool based onwhether the location (panel name and port number information) enteredand/or received for the current cable's unique identifier matches thepreviously stored location for that cable, where the cable is identifiedbased on its scanned unique identifier (108). The port number may thenbe automatically incremented (110), and the cable management tooldetermines whether another cable unique identifier is to be scanned toperform another “scan and verify” operation (112). If there areadditional cables to be verified, the process for the “scan and verify”mode 50 is repeated by looping back to entering/receiving the panel nameinformation and port number information for the next cable beingverified (104). Otherwise, the process for the “scan and verify” mode 50ends (100).

FIG. 16 is a logic flowchart 1600 describing a process implemented bythe cable management tool for a “find” mode 60, according to anon-limiting exemplary embodiment of the present disclosure. Once again,as seen therein, the cable management tool may initially start executionbased on two scenarios (72): first, a new installation environment whereunique ID cables have not yet been fully installed (74); or second, apreviously installed environment where unique ID cables have alreadybeen partially, or fully, installed (76). Upon starting execution of thecable management tool (72), the cable management tool may enter the“scan” mode 40, the “scan and verify” mode 50, or the “find” mode 60.

As previously described, the cable management tool implements the “find”mode 60 by identifying a first cable end from scanning the uniqueidentifier at a first location (120). By scanning the unique identifier,the cable management tool looks up the corresponding cableidentification code to establish as the first cable end, with theintention of finding the corresponding second cable end using the “find”mode 60.

Thereafter, the user travels to a second location to begin scanningunique identifiers off of cable ends found at the second location in aneffort to find the matching second cable end. So at this secondlocation, the unique identifier off a target cable end is scanned andthe cable management tool identifies the cable identification code forthe target cable end (122). Then the cable identification codes for thefirst cable end and the target cable end are compared to see if theymatch (124). A match may identify the same cable identification codewith their respective location code (e.g., 10000090A and 10000090B).

If the cable management tool determines there is a match, a PASS statusis reported (126), such as via the display of the mobile computingdevice and/or via a first audible tone emitted by the mobile computingdevice 20. If the cable management tool determines there is not a match,then a FAIL status is reported (128), such as via the display of themobile computing device and/or via a second audible tone different thanthe first audible tone emitted by the mobile computing device.

When the cable management tool reports the FAIL status, the uniqueidentifier at a different target cable end at the second location isscanned to continue the search for the other end to the first cable end(122). This looping process may continue until a match is found topresent the PASS status (126), or until the user exits the “find” mode.

FIG. 17 shows an exemplary structured cabling system 1000 where a firstcabinet (e.g., Cabinet A) is located a distance away from a secondcabinet (e.g., Cabinet B) and connected using bulk cable. A cable 150 isused to connect connector panels (e.g., modular patch panels or fiberenclosure trays) mounted in cabinet A to connector panels mounted incabinet A in a one-to-one manner. In this structured cabling system1000, cabinet A and cabinet B are directed connected in a one-to-onemanner using one or more cable runs of the cable 150 that are mountedbetween the connector panels installed into the respective cabinet A andcabinet B. According to the structured cabling system 1000, the cable150 may be representative of one or more distinct runs of the same typeof cable.

In the one-to-one wiring method as shown in the structured cablingsystem 1000, port No. 1 on a patch panel or fiber enclosure in cabinet Awill be cabled to port No. 1 in the corresponding patch panel or fiberenclosure in cabinet B. So during an installation process the installeris tasked with keeping track of the cable 150 to ensure it is the propercable to being routed to the correct ports. In past implementations, theinstallers may have installed temporary labels onto the cable 150 tohelp with identification during the cable pulling process. However, insituations where the cable 150 is not labelled with pulling labels, orpulling labels are dislodged in the installation process, additionaltime must be spent troubleshooting and identifying the cable 150 toinstall them in the proper corresponding positions.

Besides pulling cable and terminating connectors on cable ends, thesystem installer may also provide documentation of pulled cables to acustomer. Structured cabling is used to connect two endpoints indifferent locations, and therefore documentation of structured cablingfocuses on to and from locations, specifically information thatdescribes which port a first cable end is from (one terminated end ofthe cable or near end) to which port a second cable end to the samecable is going (other terminated end of the same cable or far end).

In an effort to aid in the management of the cable 150 used in thestructed cabling system 1000, the cable 150 itself is a bulk cablehaving pre-printed unique identifiers 151 placed directly on the cablejacket at predetermined intervals as it is manufactured and wound onto acable spool prior to installation, as shown in FIG. 18. The uniqueidentifiers 151 may be a multi-part barcode that includes a uniquenumber identifying each individual spool of cable, and may also includea distance marker that indicates the distance of cable unwound from thespool, as well as other descriptive information. The unique identifiers151 are described herein as being barcodes for exemplary purposes,although other types unique identifiers may be used (e.g.,machine-readable codes such as QR codes, or unique alpha-numeric codefor image recognition).

FIG. 18 shows a partial view of the cable 150 that includes twoinstances of the unique identifier 151 spaced apart by a predeterminedinterval distance. Whereas the unique identifier 13 illustrated in FIG.2 is printed onto labels 12, the unique identifier 151 shown in FIG. 18is pre-printed directly onto the cable 150. The unique identifier 151 isprinted at locations to be spaced apart by the predetermined intervallength (e.g., 12 inches or less, 18 inches or less, 24 inches or less,or another predetermined interval distance). The unique identifier 151is scanned by the cable management tool to then identify a cableidentification code for the cable from which the unique identifier 151was scanned from. With the cable identification code, the cablemanagement tool may further obtain cable production data such as, butnot limited to, cable manufacturing information (e.g., cable length,part number, cable type), quality control data, country of origin,production date, material lot number, category of cable, plenum or LSZHmaterial confirmation, test result data such as insertion loss,crosstalk, DC resistance, or other information known about the cable(hereinafter collectively referred to as the cable information). Whilein some embodiments the cable information may be stored on the mobilecomputing device 20 as part of the cable management tool, according toother embodiments the cable management tool communication with a remoteserver, via APIs, to access and download the cable information.

In addition or alternatively, according to some embodiments the cable150 may further include one or more labels that include the uniqueidentifier 151 or other information (e.g., cable information). The labelmay be attached near one or both of the cable ends, similar to thelabels 12 described in FIG. 2. The labels may be attached at a positionthat is at the predetermined distance from the cable end it is attachednearest to, or further away from.

The cable 150 may be used in the cable management system 200, where theunique identifiers 151 are scanned by the barcode scanner 30 to obtainthe corresponding information from the unique identifiers 151. Thebarcode scanner 30 may then similarly transmit the scanned informationto the mobile computing device 20 executing the cable management toolfor the cable management tool to obtain cable identification codesand/or other cable information using the scanned information. Forexample, a process for identifying the cable runs during a bulk cableinstallation process in the structured cabling system 1000 may beimplemented, at least in part, by the cable management tool according tothe processes described in flowchart 1900 shown in FIG. 19.

According to a first step in the flowchart 1900, an inventory of thenumber of cable runs needed for the installation is accounted for bydetermining how many cable runs will be used in the current installation(1901). This step may also include assigning a unique identificationcode to the cable runs and inputting the unique identification codesinto the cable management tool. Then the installer may physically pullthe number of cable runs needed (1902).

As each cable run may come from its own individual cable spool, next aninventory of the spools that are being used to pull the cable from isaccounted for by identifying the cable spools from which the cable runswill be pulled from (1903). This step may also include inputting theidentification of the cable spools into the cable management tool(1904).

Next, the cable management tool is updated to create a lookup table thatincludes a data insertion row for each of the cable runs that have beenidentified for this current installation, and associating each cable runto their unique identification code and cable information such as, forexample, its origination spool information (1905).

Next, the installer moves to a first location and inserts a first cableend into a first port at the first location (1906). After this insertionstep, the installer inputs the name of the port where the cable end hasbeen installed into the cable management tool and uses the barcodescanner 30 to scan the unique identifier 151 of the cable. The scannedinformation is received by the cable management tool running on themobile device 20 to auto-populate the cable information into the tableand assign it to the appropriate port where the first cable end has beeninstalled within the table (1907). For example, the installer maymanually enter the patch panel and port information where the cable endwas mounted into the cable management application tool (i.e.name=RoomA-panelA, port=01) and then scan the unique identifier 151located near the terminated cable so that the corresponding cableidentification code and/or cable information is auto-populated into thecable management application tool (e.g., the table) as being associatedwith the manually input patch panel and port location.

The cable management tool then determines whether there are additionalcable ends to inset into remaining ports at the first location (1908).If the cable management tool determines additional cable ends are leftfor inserting into remaining ports, then the additional cable ends areinserted into the remaining ports (1909), while also similarly scanningthe unique identifiers as the cable ends are installed into theirrespective ports (1907). This way, the cable management tool receivesthe correct identification information for assigning the proper cablesto their mounted port location at the first location. This loopedprocess is continued until no more cables are left for installation atthe first location.

When no further cables ends are left for mounting into ports at thefirst location, the installer moves to a second location where theopposite cable ends are to be inserted into their corresponding portslocated at the second location (2000).

Here at the second location, the installer uses the barcode scanner 30to scan the unique identifier 151 of the cable at the second cable end(2001). The cable management tool reads the unique identifier 151 of thecable and identifies the corresponding identification code to obtain thecorresponding cable installation location from when it was previouslyidentified and mounted at its port location at the first location. Fromthis identification, the cable management tool displays the portlocation for where the corresponding first cable end was mounted at thefirst location. Then with this information the installer determines theintended port mounting location for the second cable end at the secondlocation based on where the first cable end was mounted into the patchpanel at the first location (e.g., mirror the mounting positions).

In addition or alternatively, the cable management tool may havepre-stored information that identifies the intended port mountinglocation (e.g., not mirrored mounting positions) for the cable at thesecond location. Then after identifying the cable based on the scannedunique identifier 151, the cable management tool displays the intendedport mounting location for the second cable end based on the pre-storedinformation.

Once installed, the scanned information received by the cable managementtool running on the mobile device 20 auto-populates the cableinformation into the table and assigns it to the appropriate port wherethe second cable end has been mounted at the second location. Therefore,the cable management tool will have a record for where both the firstcable end and the second cable end for the same cable have been mountedfor future reference.

The cable management tool determines whether there are additional cableends to install into remaining ports at the second location (2002). Whenthe cable management tool determines there are cable ends remaining toinstall into ports at the second location, the remaining cable ends areinserted into the remaining ports until no more cables are left (2003),while scanning the respective unique identifier 151 as the remainingcable ends are being installed (2001). The scanning of the uniqueidentifiers ensures the cable management tool will have a record forwhere both the first cable end and the second cable end for the samecable have been mounted for future reference. As the second location maybe the location where the cable spool is located, the cables may be cutfrom the spool after being scanned here at the second location.

When all the cable ends have been mounted into their locations andaccounted for in the cable management tool, the cable management toolmay be executed to run an analysis to ensure the installation has beenaccomplished correctly (2004). The resulting cable location data (e.g.,the table) may be stored locally on the mobile device 20 or transmittedto an offsite storage device (e.g., cloud storage or server computer).

According to some embodiments, custom labels may be created by theinstaller using, for example, the cable management tool (2005). Aftercreating the custom labels, the custom labels are sent to an on-siteportable cable printer for printing (2006). The custom label may then beattached to the intended cable (2007). The custom label may includeinformation not included in the unique identifiers 151. For example, thecustom label may include one or more pieces of the cable production datathat has been downloaded based on the identification of the cable fromthe scanned unique identifier 151. The intended cable for receiving thecustom label may be located using the information gathered by the cablemanagement application tool.

According to some embodiments, the cable 150 including the uniqueidentifiers 151 that are pre-printed at the predetermined interval onthe outer layer may also be used by the cable management tool duringimplementation of the “scan” mode, the “scan and verify” mode, and/orthe “find” mode described herein. In other words, the unique identifiers151 found on the cable 150 included in the structured cabling system1000 may be scanned by the barcode scanner 30 to use the scannedinformation to implement the “scan” mode, the “scan and verify” mode,and/or the “find” mode described herein.

The process described by flowchart 1900 is a more efficient andeffective installation process which saves the installer the initialstep in traditional installation jobs of creating and pulling labels toapply them to the bulk cable as was needed previously.

So the installation process in which an installer pulls the cable fromone location to another can greatly affect the amount of time spentidentifying cables and creating relevant documentation. According tosome embodiments, the management application tool may include a digitalimaging feature that captures an image of the location (e.g., serverroom) where the cable management is taking place and include the imagealong with the generated report in a data file corresponding to thelocation.

According to some embodiments, the management application tool may savethe data files based on a room name to better manage the data files asthe cable management projects increase in scale. A database, storedlocally on the mobile computing device 20 or remotely at a cloudstorage, may also be utilized to store data files and reports generatedby the management application tool.

According to some embodiments, the cable management tool may implement agraphical user interface (GUI) that includes an increase (e.g., “+”)and/or decrease (e.g., “-”) button(s) for easily transitioning to anext, or previous, port and/or panel during any one or more of theprocesses described herein.

The present disclosure thus describes a cable management device, system,method, and application program comprising a non-transitory computerreadable storage medium that solve the problems associated with theknown cable management approaches described previously. The cablemanagement device, system, method, and non-transitory computer readablestorage medium of the present disclosure provide and/or utilize uniquecable identifiers in conjunction with intelligent software that canprovide patch field cable documentation without the hassle of manuallytracing cables and documenting their location. Once a patch field hasbeen scanned, the cable management device, system, method, andnon-transitory computer readable storage medium of the presentdisclosure can then use saved information to verify or find existingconnections.

As is readily apparent from the foregoing, various non-limitingembodiments of a cable management device, system, method, andnon-transitory computer readable storage medium have been described.While various embodiments have been illustrated and described herein,they are exemplary only and it is not intended that these embodimentsillustrate and describe all those possible. Instead, the words usedherein are words of description rather than limitation, and it isunderstood that various changes may be made to these embodiments withoutdeparting from the spirit and scope of the following claims.

What is claimed is:
 1. A cable management system comprising: a cablecomprising a plurality of unique identifiers printed on an outer layerof the cable, wherein the plurality of unique identifiers are printed ata predetermined interval along the outer layer; a barcode scannerconfigured to scan the unique identifiers printed on the cable; and amobile computing device comprising a processor, a data storage mediumstoring machine readable instructions, a communication unit, and a userinterface including a display, wherein the mobile computing device isconfigured to execute the machine readable instructions to: receive, viainputs to the user interface, first end location information for thecable; receive, from the barcode scanner, a cable identifier for thecable obtained via a scan of the unique identifier printed on the cable;and display, on the user interface, the cable identifier to associatewith the first end location.
 2. The cable management system of claim 1,wherein the mobile computing device is further configured to execute themachine readable instructions to: receive, via inputs to the userinterface, second end location information for the cable; receive, fromthe barcode scanner, the cable identifier for the cable obtained via ascan of the unique identifier printed on the cable; and display, on theuser interface, the cable identifier to associate with the second endlocation.
 3. The cable management system of claim 1, wherein the barcodescanner comprises a clip including a hook portion configured to receivethe cable and a viewing window configured to enable viewing of theunique identifier.
 4. The cable management system of claim 1, whereinthe predetermined interval is 12 inches or less.
 5. The cable managementsystem of claim 1, wherein the mobile computing device is furtherconfigured to execute the machine readable instructions to: generatelabel information corresponding to the cable; and transmit the labelinformation to a printer for printing the label information onto alabel.
 6. The cable management system of claim 1, wherein the uniqueidentifiers is used to identify at least one of cable attributeinformation, cable spool information, cable length information, or cableproduction data.
 7. A method for managing a cable installed in a cablingsystem, wherein the cable includes a plurality of unique identifiersprinted on an outer layer of the cable at a predetermined interval, themethod comprising: identifying, on a user interface displayed on adisplay of a mobile device, a first end location information for thecable; scanning a unique identifier printed on the cable with a barcodescanner; and displaying, on the user interface, the cable identifier toassociate with the first end location.
 8. The method of claim 7, furthercomprising: identifying, on the user interface, a second end locationinformation for the cable; scanning a unique identifier printed on thecable with the barcode scanner; and displaying, on the user interface,the cable identifier to associate with the second end location.
 9. Themethod of claim 7, wherein the barcode scanner comprises a clipincluding a hook portion configured to receive the cable and a viewingwindow configured to enable viewing of the unique identifier.
 10. Themethod of claim 7, wherein the predetermined interval is 12 inches orless.
 11. The method of claim 7, wherein the predetermined interval is18 inches or less.
 12. The method of claim 7, further comprising:generating label information corresponding to the cable; andtransmitting the label information to a printer for printing the labelinformation onto a label.
 13. A non-transitory storage medium configuredto store processor executable instructions for managing a plurality ofcables, wherein each of the plurality of cables include a plurality ofunique identifiers printed on an outer layer of the cable at apredetermined interval, wherein when executed by a processor theinstructions are configured to cause the processor to: receive, viainputs to a user interface, first end location information for thecable; receive, from a barcode scanner, a cable identifier for the cableobtained via a scan of the unique identifier printed on the cable; anddisplay, on the user interface, the cable identifier to associate withthe first end location.
 14. The non-transitory storage medium of claim13, wherein when executed by the processor the instructions are furtherconfigured to cause the processor to: receive, via inputs to the userinterface, second end location information for the cable; receive, fromthe barcode scanner, the cable identifier for the cable obtained via ascan of the unique identifier printed on the cable; and display, on theuser interface, the cable identifier to associate with the second endlocation.
 15. The non-transitory storage medium of claim 13, wherein thepredetermined interval is 12 inches or less.
 16. The non-transitorystorage medium of claim 13, wherein the predetermined interval is 18inches or less.
 17. The non-transitory storage medium of claim 13,wherein when executed by the processor the instructions are furtherconfigured to cause the processor to: generate label informationcorresponding to the cable; and transmit the label information to aprinter for printing the label information onto a label.
 18. Thenon-transitory storage medium of claim 13, wherein the uniqueidentifiers are used to identify at least one of cable attributeinformation, cable spool information, cable length information, orproduction data.